Skip to content

Fix: kafka 단일 broker 설정 추가 - #111

Merged
jaebeom79 merged 1 commit into
mainfrom
develop
May 30, 2026
Merged

Fix: kafka 단일 broker 설정 추가#111
jaebeom79 merged 1 commit into
mainfrom
develop

Conversation

@jaebeom79

Copy link
Copy Markdown
Contributor

📢 기능 설명

factor <= broker
일 때 kafka 작동

@jaebeom79
jaebeom79 merged commit f8745f4 into main May 30, 2026
1 check passed

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request configures Kafka internal topics for a single-broker production environment in docker-compose.prod.yml to prevent consumer group join failures. The reviewer suggests further optimizing resources in this memory-constrained environment by reducing the partition counts for internal topics to 1.

Comment thread docker-compose.prod.yml
Comment on lines +208 to +210
KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1
KAFKA_TRANSACTION_STATE_LOG_REPLICATION_FACTOR: 1
KAFKA_TRANSACTION_STATE_LOG_MIN_ISR: 1

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

현재 설정된 KAFKA_HEAP_OPTS: "-Xms256m -Xmx256m"와 같이 메모리가 매우 제한된 환경(t3.small 등)에서 단일 브로커를 운영할 때, 내부 토픽(__consumer_offsets, __transaction_state)의 기본 파티션 수(기본값 각각 50개)는 불필요하게 많은 파일 디스크립터와 메모리 오버헤드를 발생시킬 수 있습니다.

따라서 단일 브로커 환경에서는 이 내부 토픽들의 파티션 수를 1개로 줄여 리소스를 최적화하는 것을 권장합니다.

      KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1
      KAFKA_OFFSETS_TOPIC_NUM_PARTITIONS: 1
      KAFKA_TRANSACTION_STATE_LOG_REPLICATION_FACTOR: 1
      KAFKA_TRANSACTION_STATE_LOG_MIN_ISR: 1
      KAFKA_TRANSACTION_STATE_LOG_NUM_PARTITIONS: 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant